Systems, methods, and computer program products for load adaptive streaming

ABSTRACT

Methods, systems, and computer program products that allow for the load adaptive downloading, processing, and rendering of video by a video processing client, where the downloading is adaptive to the processing load of a computing system on which a video processing client operates.

BACKGROUND

Adaptive video streaming is a method by which a receiving device or system selects a bitstream from among a set of bitstreams, each representing the same video interval, where the selected bitstream represents the highest quality level that can be sustained by the communications infrastructure and display. Each bitstream in the set of bitstreams may represent a different level, where a higher level corresponds to a higher bitrate and resolution. As a result, the bitstream at a higher level requires more processing time than the bitstream at a next lower level.

Not all platforms will have sufficient processing power to decode, with sufficient speed, the level that can be sustained by the network and display, however. Most notably, low powered personal computers (PCs) (such as laptops and older desktop PCs) may struggle with processing bitstreams at such a level. Furthermore, some computers, especially laptops, use dynamic frequency scaling. This allows the frequency of the central processing unit (CPU) to adapt, depending on the heat and power properties. This will affect the available processing power as well, possibly making it difficult for a computer to handle a bitstream level that is chosen on the basis of network and display capabilities. In addition, the CPUs may be shared with other running processes (programs), which reduces the available processing capacity for video processing. Therefore, the selection of a particular bitstream in an adaptive streaming system needs to consider the available processing power.

BRIEF DESCRIPTION OF THE DRAWINGS/FIGURES

FIG. 1 is a block diagram of an exemplary video system, according to an embodiment.

FIG. 2 illustrates a sorted list showing excess times to deliver frames, according to an embodiment.

FIG. 3A is a flow chart illustrating the selection of a lower decoding level, according to an embodiment.

FIG. 3B is a flow chart illustrating the selection of a higher decoding level, according to an embodiment.

FIG. 4 is a flow chart illustrating the flushing of a coded picture buffer, according to an embodiment.

FIG. 5 is a block diagram illustrating an exemplary computing system with which the processing described herein may be implemented, according to an embodiment.

In the drawings, the leftmost digit(s) of a reference number identifies the drawing in which the reference number first appears.

DETAILED DESCRIPTION

An embodiment is now described with reference to the figures, where like reference numbers indicate identical or functionally similar elements. While specific configurations and arrangements are discussed, it should be understood that this is done for illustrative purposes only. A person skilled in the relevant art will recognize that other configurations and arrangements can be used without departing from the spirit and scope of the description. It will be apparent to a person skilled in the relevant art that this can also be employed in a variety of other systems and applications other than what is described herein.

Disclosed herein are methods, systems, and computer program products that allow for the load adaptive downloading, processing, and rendering of video by a video processing client, where the downloading is adaptive to the processing load of a computing system on which a video processing client operates.

Generally, the processing power required to decode and render video streams increases monotonically with bitrate and resolution of the streams. The load adaptive functionality described herein may provide a smooth playback at a specific level, thus avoiding excessive stutter on the client. The load adaptive process chooses an appropriate decode level (i.e., an appropriate bitstream from the set of bitstreams) that is sustainable (i.e. a bitstream that can be decoded in real-time given the current system processing capabilities), and with the best visual quality. An embodiment of the process, which includes a predictive feedback based process, will initially start with no prior knowledge of the video system, and will acquire knowledge by analyzing performance data received from the video system. A decision for the maximum sustainable decode level may be made prior to download of a video segment, and will be based on the recent performance history of the video system. Occasionally, selection of a decode level may, under specific conditions, be followed by flushing some of the already-downloaded video data in an embodiment.

FIG. 1 illustrates an exemplary video processing system 100 in which load adaptive streaming may take place, according to an embodiment. A video frame 110 is received and placed in a coded picture buffer (CPB) 120. The number of frames held in CPB 120 will vary, depending on the rate at which frames are received and the rate at which they are read out. Video frames that are read from CPB 120 are decoded by video decoder 130. Decoded frames may then be stored in a first frame queue 140. After passing through queue 140, a decoded frame is then processed by video processing module(s) 150. The processing performed by module(s) 150 may include, for example, scaling, format conversion, and filtering operations. Processed frames may then be passed to a renderer 170, via a second frame queue 160.

In an embodiment, the load adaptive streaming process selects an initial playback bitrate from previously stored client configuration information. The client stores the maximum load adaptive decode level previously used during playback. For example, on Windows™, the client can store the maximum load adaptive level in the registry, in an embodiment. In the absence of a previous stored configuration, the load adaptive functionality can start from the lowest level.

From this initial state, a new decode level may be chosen, based on processing conditions, i.e., on the load being placed on the host computing system. There are many indications that could be used to determine whether the system can handle the load. Examples include CPU usage (as measured by the ratio of the amount of time in which the CPU is active to the time spent idle, for example) or the rate or extent of dropping of video frames. CPU usage may be used, but in an embodiment this is not considered as a measure as there is no strong correlation between the dead-line driven nature of the video system (i.e., the requirement for a certain number of frames per unit time) and the average load of a CPU. The rate of dropping frames is a useful measure, although it is reactive. A useful measure would indicate when the load is approaching the limit of a system. A video system must render a frame every frame period. From this follows that, on average, it must produce a frame every frame period, such that the second frame queue is never depleted.

The load-adaptive streaming process as described herein may use, as inputs, one or more of a variety of performance measures relating to the operations and delays of a system such as system 100. The following performance measurements may be used for load adaptive streaming functionality, according to an embodiment. In order to minimize communication overhead between the client video system and the load adaptive streaming process, the measurements may be assembled in the client's video system in a sample collection buffer and relayed to the load adaptive streaming process periodically.

A. Time to deliver a frame: The time to deliver a frame is a measurement of the total system time spent for decoding and video processing operations.

In an embodiment, the excess time to deliver a frame with respect to the frame period (referred to herein as excess frame time) may be used as a comparable measure. If the frame period is 40 ms and the time to deliver a frame is 50 ms then the excess frame time is 10 ms. The excess frame time is −10 ms when the time to deliver a frame is 30 ms. As a video system typically employs a frame queue, the delivery time is averaged over the frames in the queue. As can be concluded from empirical measurements, the time to deliver a frame varies considerably; however as all frames need to be delivered in time, the processing described here needs to consider only the outliers, i.e., the frames that take the longest time to process. In such an embodiment, a sorted list of the largest (or maximum) excess delivery times is maintained; the average of a subset of these maximum values is then calculated. In an embodiment, this subset represents a selected range of these maximum values. This average is used for comparison to a decision threshold. This average may be viewed as an average of a range of maximum excess delivery times. Note that the “excess delivery times” are determined as a function (e.g., the mean) of the delivery times of frames in the second queue in an embodiment.

FIG. 2 illustrates such a sorted list. The height of each vertical bar represents an excess frame delivery time. These heights, or times, may be averaged over a configurable range, for example 2 to 5, to derive an average of a range of maximum excess delivery times. This value may then be compared to a threshold value. There are two thresholds. If this average is below the lower threshold then a higher level can be selected. If this average is exceeding the higher threshold, this implies that the load of the host machine is excessive and leads to a shift to a lower decoding level.

In an embodiment, the difference between the two thresholds is larger than the expected performance increase. The lower threshold may be derived dynamically from the difference in resolution. In addition, in an embodiment, the thresholds may be derived dynamically in the client video system during operation. Alternatively, the thresholds may be configured statically by a remote server. The thresholds may also be stored locally at the client video system, and may be read at startup.

B. Total number of frames in the frame queue: Note that this value is dynamic

C. Dropped frame count over a predetermined period.

D. Current decode level.

E. The amount of video data in download buffers

F. The video resolution for each streaming level.

The choice of a lower decoding level is illustrated in FIG. 3A, according to an embodiment. At 310, the highest previous decode level is retrieved and is used as the default decode level initially. At 315, a determination is made as to whether the average of the range of maximum excess delivery times is greater than a first threshold value over a predetermined period. If so, then at 320, the next segment of video is downloaded at the next lower decode level. In an embodiment, a waiting period may be imposed before switching to the lower decode level. At 325, the coded picture buffer CPB is flushed. As will be described in greater detail below, this flushing is not generally complete, so that some frames will remain in the CPB after flushing.

The choice of a higher decode level is illustrated in FIG. 3B, according to an embodiment. At 360, a determination is made as to whether the average of the range of maximum excess delivery times is less than a second threshold value over a predetermined time period. If so, then at 365, the next segment of video is downloaded at the next higher decode level.

In an embodiment, a minimum observation period may be implemented, such that a lower decode level is chosen only if the average time to deliver exceeds the threshold for this minimum observation period. In an embodiment, this time period may be zero seconds, but in other embodiments, this minimum observation period may be non-zero. Analogously, another minimum observation period may be implemented, such that a higher decode level is chosen only if the average time to deliver is below the defined threshold for this minimum observation period.

The flushing of the CPB (325 above) is performed when the proper condition(s) are met, and only performed to a certain extent, according to an embodiment. This is illustrated in FIG. 4. At 410, a determination is made as to whether the percentage of dropped frames exceeds a frame drop threshold. If so, then the frames currently in the pipeline are not being processed quickly enough, and it becomes advantageous to remove some of the frames from the CPB. This flushing of the CPB takes place at 420. In an embodiment, the percentage of dropped frames depends on the total number of frames dropped over a predefined period.

The extent of the flushing may vary according to system conditions. Generally, not every frame will be removed. A flush may be performed when the current level results in dropped frames. In an embodiment, the percentage of dropped frames will determine the aggressiveness of the flush. In such an embodiment, if the percentage of dropped frames is less than 2%, no flush is needed. If the percentage of dropped frames is between 2% and 15%, the CPB is flushed to the extent that 11 seconds of video are kept in the CPB. If the percentage of dropped frames exceeds 15%, the CPB is flushed to the extent that 6 seconds of video are retained in the CPB. In alternative embodiments, the dropped frame threshold percentages may vary and the extent of flushing may vary.

Note that in some video systems, a rate adaptive streaming process may also be in place. In such a context, there may be a relationship between the rate adaptive and load adaptive algorithms. The rate adaptive algorithm may rely on buffering several seconds of video data to avoid re-buffering, whereas the load adaptive algorithm avoids excessive stutter by choosing an appropriate decode level and by sometimes purging downloaded data from the CPB of the client. In an embodiment, the client chooses the lower of the two levels recommended by the rate adaptive process and the load adaptive process.

One or more features disclosed herein may be implemented in hardware, software, firmware, and combinations thereof, including discrete and integrated circuit logic, application specific integrated circuit (ASIC) logic, and microcontrollers, and may be implemented as part of a domain-specific integrated circuit package, or a combination of integrated circuit packages. The term software, as used herein, refers to a computer program product including at least one computer readable medium having computer program logic stored therein to cause a computer system to perform one or more features and/or combinations of features disclosed herein. The computer readable medium may be transitory or non-transitory. An example of a transitory computer readable medium may be a digital signal transmitted over a radio frequency or over an electrical conductor, through a local or wide area network, or through a network such as the Internet. An example of a non-transitory computer readable medium may be a compact disk, a flash memory, RAM, ROM, or other data storage device.

In an embodiment, some or all of the processing described herein may be implemented as software or firmware. Such a software or firmware embodiment is illustrated in the context of a computing system 500 in FIG. 5. System 500 may include one or more central processing unit(s) (CPU), shown as processor(s) 520, and a body of memory 510 that includes one or more non-transitory computer readable media that store computer program logic 540. Memory 510 may be implemented as a read-only memory (ROM) or random access memory (RAM) device, for example. Processor(s) 520 and memory 510 may be in communication using any of several technologies known to one of ordinary skill in the art, such as a bus or a point-to-point interconnect. Computer program logic 540 contained in memory 510 may be read and executed by processor(s) 520. In an embodiment, one or more I/O ports and/or I/O devices, shown collectively as I/O 530, may also be connected to processor(s) 520 and memory 510. In an embodiment, I/O 530 may include the display of the user's computing device.

In the embodiment of FIG. 5, computer program logic 540 may include a module 550 responsible for monitoring the processing load of the system 500. As discussed above, this may include determining the average of the range of maximum excess delivery times and determining the percentage of dropped frames. Computer program logic 540 may also include a module 560 responsible for increasing the decode level for the next interval of video to be downloaded. Computer program logic 540 may include a module 570 responsible for decreasing the decode level for the next interval of video to be downloaded. Computer program logic 540 may also include a module 580 responsible for flushing the CPB under the circumstances described above. Note that the operation of modules 560-580 depends on the load conditions detected by load monitoring logic 550.

In an embodiment, constants and definitions in the processing described herein may also be programmable, along with a set of default parameters. These may include the following configuration parameters:

-   a) Enable/Disable load adaptive functionality: The client is     configured to either enable or disable the load adaptive     functionality. On some platforms such as consumer electronic     devices, this functionality may be disabled. -   b) Minimum amount of video data in the download buffer: The client     should not flush the entire contents of the data buffer; a minimum     amount of data may be retained, as discussed above, to prevent     playback pause caused by re-buffering. -   c) Maximum history period: The load adaptive streaming process may     use recent history to predict the maximum sustainable decode level     for the video system. This value sets the width of the window of     recently elapsed time to predict performance of the video system. -   d) Minimum observation period for choosing a higher decode level:     The minimum time for a consistent performance increase which must be     observed prior to up-switch to a higher decode level. -   e) Minimum observation period before choosing a lower decode level:     The minimum time that is observed prior to down-switch. In an     embodiment, this duration is observed even it is leads to stutter. -   f) Maximum number of frames in the sample collection buffer: The     collection buffer, which shall be in the client video system,     accumulates the measurements mentioned above. This value determines     the number of measurement vectors that must be accumulated prior to     sending the accumulated data to the load adaptive process. -   g) Threshold to trigger a switch to a higher decoding level. In some     embodiments this might be derived from the difference in resolution     between the current level and next level. -   h) Threshold to trigger a switch to a lower decoding level. -   i) Frame drop threshold: The maximum percentage of dropped frames     over an historical period. This value establishes a threshold for     the flushing requirements, as discussed above.

Methods and systems are disclosed herein with the aid of functional building blocks illustrating the functions, features, and relationships thereof. At least some of the boundaries of these functional building blocks have been arbitrarily defined herein for the convenience of the description. Alternate boundaries may be defined so long as the specified functions and relationships thereof are appropriately performed.

While various embodiments are disclosed herein, it should be understood that they have been presented by way of example only, and not limitation. It will be apparent to persons skilled in the relevant art that various changes in form and detail may be made therein without departing from the spirit and scope of the methods and systems disclosed herein. Thus, the breadth and scope of the claims should not be limited by any of the exemplary embodiments disclosed herein. 

What is claimed is:
 1. A method of adaptive video streaming, comprising: in a client computing device, determining whether an average of maximum excess times to deliver a frame of downloaded video exceeds a first threshold, wherein the average is calculated over a selected range of a sorted list of excess times to deliver frames within a time period; and if so, downloading a next interval of video at a lower decoding level.
 2. The method of claim 1, wherein the downloading of next interval of video at a lower decoding level takes place after a minimum observation period.
 3. The method of claim 1, further comprising: determining if a percentage of dropped frames exceeds a frame drop threshold; and if so, flushing a coded picture buffer to eliminate a portion of the buffered downloaded frames contained in the coded picture buffer, performed after said downloading of the next interval of video at the lower decoding level.
 4. The method of claim 3, wherein the percentage of dropped frames is determined over a predefined historical period.
 5. The method of claim 3, wherein the number of frames flushed from the coded picture buffer is dependent on the percentage of dropped frames.
 6. The method of claim 1, further comprising: determining whether the average is less than a second threshold; and if so, downloading the next interval of video at a higher decoding level, wherein the second threshold is automatically calculated such that the higher decoding level does not exceed performance capabilities of a system implementing said method.
 7. The method of claim 6, wherein said downloading of the next interval of video at a higher decoding level takes place after a minimum observation period.
 8. The method of claim 6, wherein the next interval of video is downloaded in a higher decoding level only when the average time to deliver a frame of downloaded video is less than the second threshold by a predetermined amount.
 9. The method of claim 6, wherein one or more of the first and second thresholds is derived dynamically during operation of the client computing device.
 10. The method of claim 6, wherein one or more of the first and second thresholds is determined statically by a server in communication with the client computing device.
 11. The method of claim 6, wherein one or more of the first and second thresholds is stored locally at the client computing device and read upon start up of the client computing device.
 12. The method of claim 1, wherein downloading of a video stream begins at a decoding level equal to a maximum previous decode level.
 13. A computer program product for adaptive video streaming in a client computing device, including a non-transitory computer readable medium having computer program logic stored therein, the computer program logic including: logic for determining whether an average of maximum excess times to deliver a frame of downloaded video exceeds a first threshold, wherein the average maximum time to deliver is calculated over a selected range of a sorted list of excess time to deliver frames within a time period; and logic for downloading a next interval of video at a lower decoding level if the average time to deliver a frame of downloaded video exceeds the first threshold.
 14. The computer program product of claim 13, wherein the downloading of next interval of video at a lower decoding level takes place after a minimum observation period.
 15. The computer program product of claim 13, further comprising: logic for determining if a percentage of dropped frames exceeds a frame drop threshold; and logic for flushing a coded picture buffer to eliminate a portion of the buffered downloaded frames contained in the coded picture buffer, if the percentage of dropped frames exceeds the frame drop threshold performed after the downloading of the next interval of video at the lower decoding level.
 16. The computer program product of claim 15, wherein the percentage of dropped frames is determined over a predefined historical period.
 17. The computer program product of claim 15, wherein the number of frames flushed from the coded picture buffer is dependent on the percentage of dropped frames.
 18. The computer program product of claim 13, further comprising: logic for determining whether the average is less than a second threshold; and logic for downloading the next interval of video at a higher decoding level if the average is less than the second threshold, wherein this threshold is automatically calculated such that the higher decoding level does not exceed performance capabilities of a video streaming system that incorporates said computer program product.
 19. The computer program product of claim 18, wherein the downloading of the next interval of video at a higher decoding level takes place after a minimum observation period.
 20. The computer program product of claim 18, wherein the next interval of video is downloaded in a higher decoding level only when the average time to deliver a frame of downloaded video is less than the second threshold by a predetermined amount.
 21. The computer program product of claim 18, wherein one or more of the first and second thresholds is derived dynamically during operation of the client computing device.
 22. The computer program product of claim 18, wherein one or more of the first and second thresholds is determined statically by a server in communication with the client computing device.
 23. The computer program product of claim 18, wherein one or more of the first and second thresholds is stored locally at the client computing device and read upon start up of the client computing device.
 24. The computer program product of claim 13, wherein downloading of a video stream begins at a decoding level equal to a maximum previous decode level.
 25. A system for adaptive video streaming, comprising: a processor; and a memory in communication with said processor, said memory for storing a plurality of processing instructions for directing said processor to: determine whether an average of maximum excess times to deliver a frame of downloaded video exceeds a first threshold, wherein the average of maximum excess times to deliver is calculated over a selected range of a sorted list of excess time to deliver frames within a time period; and if so, download a next interval of video at a lower decoding level.
 26. The system of claim 25, wherein the downloading of next interval of video at a lower decoding level takes place after a minimum observation period.
 27. The system of claim 25, wherein said memory further comprises instructions for directing said processor to: determine if a percentage of dropped frames exceeds a frame drop threshold; and if so, flush a coded picture buffer to eliminate a portion of the buffered downloaded frames contained in the coded picture buffer, performed after said downloading of the next interval of video at the lower decoding level.
 28. The system of claim 27, wherein the percentage of dropped frames is determined over a predefined historical period.
 29. The system of claim 27, wherein the number of frames flushed from the coded picture buffer is dependent on the percentage of dropped frames.
 30. The system of claim 25, wherein said memory further comprises instructions for directing said processor to: determine whether the average is less than a second threshold; and if so, download the next interval of video at a higher decoding level, wherein the second threshold is automatically calculated such that the higher decoding level does not exceed performance capabilities of a video streaming system.
 31. The system of claim 30, wherein the downloading of the next interval of video at a higher decoding level takes place after a minimum observation period.
 32. The system of claim 30, wherein the next interval of video is downloaded in a higher decoding level only when the average time to deliver a frame of downloaded video is less than the second threshold by a predetermined amount.
 33. The system of claim 30, wherein one or more of the first and second thresholds is derived dynamically during operation of the system.
 34. The system of claim 30, wherein one or more of the first and second thresholds is determined statically by a server in communication with the system.
 35. The system of claim 30, wherein one or more of the first and second thresholds is stored locally at the system and read upon start up.
 36. The system of claim 25, wherein downloading of a video stream begins at a decoding level equal to a maximum previous decode level. 